Skip to content

Conversation

rhshadrach
Copy link
Member

@rhshadrach rhshadrach added this to the 2.3.3 milestone Aug 24, 2025
@rhshadrach rhshadrach added the Strings String extension data type and string data label Aug 24, 2025
@@ -315,6 +315,37 @@ the :meth:`~pandas.Series.str.decode` method now has a ``dtype`` parameter to be
able to specify object dtype instead of the default of string dtype for this use
case.

:meth:`Series.values` now returns an :class:`~pandas.api.extensions.ExtensionArray`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we be more specific that this is a StringArray?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Pushes up glasses from nose] That is only true when not backed by PyArrow. With PyArrow, it's technically a subclass of BaseStringArray but not StringArray.

But being less technical, I tend to think of it as "ndarray vs ExtensionArray", knowing that the extension arrays specialize corresponding to dtypes. So I personally think this is okay.

No objection to changing though if you prefer StringArray or BaseStringArray.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fair points all around.

@jbrockmendel
Copy link
Member

small comment, otherwise LGTM

@jbrockmendel jbrockmendel merged commit 5b6140c into pandas-dev:main Aug 26, 2025
12 checks passed
@jbrockmendel
Copy link
Member

thanks @rhshadrach

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Docs Strings String extension data type and string data
Projects
None yet
Development

Successfully merging this pull request may close these issues.

API: return value of .values for Series with the future string dtype (numpy array vs extension array)
2 participants